Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67054539732a73d24513bc80da7a77bda50b43cf3ba4bbe1a8de39476ab97684

Tx prefix hash: 8657a9034d84d3656fe382772a7e00bc1494ef30b89cab1cd8fb5728ea88228c
Tx public key: ce515f3ee5f1e2d3f88dbe194ce0fbbc1787d569be3a53ddc59ce7842b84d69e
Timestamp: 1580267349 Timestamp [UCT]: 2020-01-29 03:09:09 Age [y:d:h:m:s]: 04:339:03:11:31
Block: 54674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133011 RingCT/type: yes/0
Extra: 01ce515f3ee5f1e2d3f88dbe194ce0fbbc1787d569be3a53ddc59ce7842b84d69e02110000000149b77a3d000000000000000000

1 output(s) for total of 404.429817908000 dcy

stealth address amount amount idx
00: a93da7549fa06c69b41f8e919a6e7ca315438bdc4e2ae581518324ab5073d55e 404.429817908000 101130 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": 54684, "vin": [ { "gen": { "height": 54674 } } ], "vout": [ { "amount": 404429817908, "target": { "key": "a93da7549fa06c69b41f8e919a6e7ca315438bdc4e2ae581518324ab5073d55e" } } ], "extra": [ 1, 206, 81, 95, 62, 229, 241, 226, 211, 248, 141, 190, 25, 76, 224, 251, 188, 23, 135, 213, 105, 190, 58, 83, 221, 197, 156, 231, 132, 43, 132, 214, 158, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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