Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff2fd903337432bd4932776211b1eee1803cf0ba57a3a5cb387f7a324f0de2ec

Tx prefix hash: d4a34e32faf53572e0a06975ec9855d7acddb2028ba7293ce33dbfd1f0bebebc
Tx public key: 49eda9a1f724f23379f8af236f0e51b2de67f8c490564a774faf80eb6c6af914
Timestamp: 1724992074 Timestamp [UCT]: 2024-08-30 04:27:54 Age [y:d:h:m:s]: 00:134:14:24:48
Block: 1098928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96284 RingCT/type: yes/0
Extra: 0149eda9a1f724f23379f8af236f0e51b2de67f8c490564a774faf80eb6c6af91402110000000491e13c04000000000000000000

1 output(s) for total of 0.607980000000 dcy

stealth address amount amount idx
00: a0c285e4bbe5e4ce44826b70a7c839a0a5ad4036473828fe18905da6acdad191 0.607980000000 1574813 of 0

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": 1098938, "vin": [ { "gen": { "height": 1098928 } } ], "vout": [ { "amount": 607980000, "target": { "key": "a0c285e4bbe5e4ce44826b70a7c839a0a5ad4036473828fe18905da6acdad191" } } ], "extra": [ 1, 73, 237, 169, 161, 247, 36, 242, 51, 121, 248, 175, 35, 111, 14, 81, 178, 222, 103, 248, 196, 144, 86, 74, 119, 79, 175, 128, 235, 108, 106, 249, 20, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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