Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1cfdc04aef541c11f171ac9e686641946eacbcafcf9ce513bb2ad4ef2d44c00

Tx prefix hash: 4c9dca433070a0fdcbd050208fa1abec288b13140cd4e99bf2dbd0a73a6a04fe
Tx public key: 87cc9359d2ea3b64fb20351acebb14da4d64fbca0fe64e98e9c4171732cf3a82
Timestamp: 1649275911 Timestamp [UCT]: 2022-04-06 20:11:51 Age [y:d:h:m:s]: 02:277:10:34:54
Block: 474641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 718064 RingCT/type: yes/0
Extra: 0187cc9359d2ea3b64fb20351acebb14da4d64fbca0fe64e98e9c4171732cf3a820211000000014da16a3a000000000000000000

1 output(s) for total of 16.417898893000 dcy

stealth address amount amount idx
00: d3cbbe08c092dc9c6ead9529534cce4ee0265dadbe0cab57f301db9a925f23dc 16.417898893000 894720 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": 474651, "vin": [ { "gen": { "height": 474641 } } ], "vout": [ { "amount": 16417898893, "target": { "key": "d3cbbe08c092dc9c6ead9529534cce4ee0265dadbe0cab57f301db9a925f23dc" } } ], "extra": [ 1, 135, 204, 147, 89, 210, 234, 59, 100, 251, 32, 53, 26, 206, 187, 20, 218, 77, 100, 251, 202, 15, 230, 78, 152, 233, 196, 23, 23, 50, 207, 58, 130, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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