Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 167c7f3185abf408d506e53bdbf4d76ca043ec33cda2821f26313767e8aec24c

Tx prefix hash: 97776419abd55850d8e1166d8b83fd4634c5692c7f2c3549dc5dc875629c8beb
Tx public key: e8d2eed161158180441ec429e17c698d64d9f99bcfc9fe1ffd2a76b192e5175d
Timestamp: 1631864985 Timestamp [UCT]: 2021-09-17 07:49:45 Age [y:d:h:m:s]: 03:103:09:15:50
Block: 335471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 849678 RingCT/type: yes/0
Extra: 01e8d2eed161158180441ec429e17c698d64d9f99bcfc9fe1ffd2a76b192e5175d02110000003bfdc024ec000000000000000000

1 output(s) for total of 47.473719169000 dcy

stealth address amount amount idx
00: b7046e0fa1b7811df89ffd2571fdc9b09e062fecc68fdfeea1178e7084411bd7 47.473719169000 691574 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": 335481, "vin": [ { "gen": { "height": 335471 } } ], "vout": [ { "amount": 47473719169, "target": { "key": "b7046e0fa1b7811df89ffd2571fdc9b09e062fecc68fdfeea1178e7084411bd7" } } ], "extra": [ 1, 232, 210, 238, 209, 97, 21, 129, 128, 68, 30, 196, 41, 225, 124, 105, 141, 100, 217, 249, 155, 207, 201, 254, 31, 253, 42, 118, 177, 146, 229, 23, 93, 2, 17, 0, 0, 0, 59, 253, 192, 36, 236, 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