Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b6a3f4c97bc78ea3e63d934d7139f849203c286c90c36e22bd7c3d3b858b689d

Tx prefix hash: 41154d4c6fb4d351fc1a1e87c6c039e5d73f615e86d7091b9145adc30c344762
Tx public key: c591fa0e9a9370c00b4dfbf600c5499602a5338b76061099fb2315056dca3008
Timestamp: 1717846128 Timestamp [UCT]: 2024-06-08 11:28:48 Age [y:d:h:m:s]: 01:153:07:16:33
Block: 1039696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368140 RingCT/type: yes/0
Extra: 01c591fa0e9a9370c00b4dfbf600c5499602a5338b76061099fb2315056dca30080211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5072ca9f8617c9925d42d63cb89ed4de43ab4a57bc50fa437f051d6302beca06 0.600000000000 1508349 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1039706, "vin": [ { "gen": { "height": 1039696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5072ca9f8617c9925d42d63cb89ed4de43ab4a57bc50fa437f051d6302beca06" } } ], "extra": [ 1, 197, 145, 250, 14, 154, 147, 112, 192, 11, 77, 251, 246, 0, 197, 73, 150, 2, 165, 51, 139, 118, 6, 16, 153, 251, 35, 21, 5, 109, 202, 48, 8, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8