Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf7cf9c14816731ceacc157d95f37e77208805ba329856fae1263b4d39f242d5

Tx prefix hash: bebf169a6f941f3b26b8abeed4efc8c2d8972825b03077b20579109d76dd67dd
Tx public key: 3d1b06adcd36e26d19a6eeaf262cf1ac45e5efd3b2ced693cf8317cc4eb4caa0
Timestamp: 1577712802 Timestamp [UCT]: 2019-12-30 13:33:22 Age [y:d:h:m:s]: 05:169:14:35:17
Block: 35061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1270932 RingCT/type: yes/0
Extra: 013d1b06adcd36e26d19a6eeaf262cf1ac45e5efd3b2ced693cf8317cc4eb4caa00211000000074943cd9f000000000000000000

1 output(s) for total of 469.709352220000 dcy

stealth address amount amount idx
00: 4847bc9dfa158b4364e3fbafc0c8eaae97771fe3480037b28d19d600953e3ce7 469.709352220000 59054 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": 35071, "vin": [ { "gen": { "height": 35061 } } ], "vout": [ { "amount": 469709352220, "target": { "key": "4847bc9dfa158b4364e3fbafc0c8eaae97771fe3480037b28d19d600953e3ce7" } } ], "extra": [ 1, 61, 27, 6, 173, 205, 54, 226, 109, 25, 166, 238, 175, 38, 44, 241, 172, 69, 229, 239, 211, 178, 206, 214, 147, 207, 131, 23, 204, 78, 180, 202, 160, 2, 17, 0, 0, 0, 7, 73, 67, 205, 159, 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