Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a75beed1af3aa22c60fd21c9df00cbc827bdb72223723d8838167f1a41f86cf

Tx prefix hash: 1f87dbf92c7a25700f9b022d65322bdda94866c3975954e3c9fb956b450910cb
Tx public key: 97df486298ddfd20ee3ad969d9544ea1362c0841ae9a4b5b1cb90c7094efc46d
Timestamp: 1714217155 Timestamp [UCT]: 2024-04-27 11:25:55 Age [y:d:h:m:s]: 01:016:16:42:18
Block: 1009607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272882 RingCT/type: yes/0
Extra: 0197df486298ddfd20ee3ad969d9544ea1362c0841ae9a4b5b1cb90c7094efc46d0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64c430966d19674278d4c5e460dc28543e86b8eaa838c62190c3cc81cee20d51 0.600000000000 1471331 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": 1009617, "vin": [ { "gen": { "height": 1009607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64c430966d19674278d4c5e460dc28543e86b8eaa838c62190c3cc81cee20d51" } } ], "extra": [ 1, 151, 223, 72, 98, 152, 221, 253, 32, 238, 58, 217, 105, 217, 84, 78, 161, 54, 44, 8, 65, 174, 154, 75, 91, 28, 185, 12, 112, 148, 239, 196, 109, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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