Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0070033933caa264a4404ed9cb6289675a2122572647cf9668b4f2db2e76971f

Tx prefix hash: d6b276ccd6e36e7f8fd93d651da591c49e095b627be4171e3454f5798e487b1d
Tx public key: acd64d36171294d7f0c118cf9240836d60e8dc2a867695aa9db7f9c67a3d26f8
Timestamp: 1582546434 Timestamp [UCT]: 2020-02-24 12:13:54 Age [y:d:h:m:s]: 05:095:15:40:27
Block: 71645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221576 RingCT/type: yes/0
Extra: 01acd64d36171294d7f0c118cf9240836d60e8dc2a867695aa9db7f9c67a3d26f80211000000568a2ee0d9000000000000000000

1 output(s) for total of 355.362133408000 dcy

stealth address amount amount idx
00: df9ce4169afd98b6556f2f4333085d7696a548f37d29f7a6f977e49aa12970e1 355.362133408000 132334 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": 71655, "vin": [ { "gen": { "height": 71645 } } ], "vout": [ { "amount": 355362133408, "target": { "key": "df9ce4169afd98b6556f2f4333085d7696a548f37d29f7a6f977e49aa12970e1" } } ], "extra": [ 1, 172, 214, 77, 54, 23, 18, 148, 215, 240, 193, 24, 207, 146, 64, 131, 109, 96, 232, 220, 42, 134, 118, 149, 170, 157, 183, 249, 198, 122, 61, 38, 248, 2, 17, 0, 0, 0, 86, 138, 46, 224, 217, 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