Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a84c61ddc6e20ce2e920f543277f53f7e05fb16240f71bedaccb53b863b8196f

Tx prefix hash: df6f0a9781d965f7b50ed231950ca1f61f0599a3a604229450e068263613fecd
Tx public key: c7988bd4d636655b2b7a6403db67d9867f8cabe2539bfa4601c2f84b8b42b73e
Timestamp: 1702282096 Timestamp [UCT]: 2023-12-11 08:08:16 Age [y:d:h:m:s]: 01:043:13:48:25
Block: 910663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292462 RingCT/type: yes/0
Extra: 01c7988bd4d636655b2b7a6403db67d9867f8cabe2539bfa4601c2f84b8b42b73e021100000007faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cacd719c2e6d058b3456686273cd92b62f2feca2e60303c1d5d6260f1aa8e55 0.600000000000 1367828 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": 910673, "vin": [ { "gen": { "height": 910663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cacd719c2e6d058b3456686273cd92b62f2feca2e60303c1d5d6260f1aa8e55" } } ], "extra": [ 1, 199, 152, 139, 212, 214, 54, 101, 91, 43, 122, 100, 3, 219, 103, 217, 134, 127, 140, 171, 226, 83, 155, 250, 70, 1, 194, 248, 75, 139, 66, 183, 62, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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