Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc64cff86ef1de92adcd12487d6cc687de34c9e04a1f4afb59e80e62afcf59f6

Tx prefix hash: c4bb4e5c72ff9ec4c7546b84fc87ed7f2aca1a1f72e5b857683038c17204dc8b
Tx public key: 784a6294cdfec3326a8182fbaeaf0d3d321bd172fb1049ca743a2fd0eaf79f3b
Timestamp: 1710476511 Timestamp [UCT]: 2024-03-15 04:21:51 Age [y:d:h:m:s]: 01:084:06:06:58
Block: 978621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321236 RingCT/type: yes/0
Extra: 01784a6294cdfec3326a8182fbaeaf0d3d321bd172fb1049ca743a2fd0eaf79f3b0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 574b9e9efce77736c7ba8b2eca6bf72fa886067b25a51a396cdcea51066e94c8 0.600000000000 1438648 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": 978631, "vin": [ { "gen": { "height": 978621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "574b9e9efce77736c7ba8b2eca6bf72fa886067b25a51a396cdcea51066e94c8" } } ], "extra": [ 1, 120, 74, 98, 148, 205, 254, 195, 50, 106, 129, 130, 251, 174, 175, 13, 61, 50, 27, 209, 114, 251, 16, 73, 202, 116, 58, 47, 208, 234, 247, 159, 59, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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