Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b39b4422581c267cf37e31a4b9196dcf5c7b5ce4f9f655cc686acbbc43dcd9a

Tx prefix hash: 172594763a994303867e97d58bd1ad923014857c7b65b5d51094f714b01e1542
Tx public key: ca2741fc2361d5bd2bcbd4d558f28d67b27c56f9d2a0cef57dd8ec0d61b5213b
Timestamp: 1581945791 Timestamp [UCT]: 2020-02-17 13:23:11 Age [y:d:h:m:s]: 04:275:05:39:26
Block: 66630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089245 RingCT/type: yes/0
Extra: 01ca2741fc2361d5bd2bcbd4d558f28d67b27c56f9d2a0cef57dd8ec0d61b5213b0211000000010aca7173000000000000000000

1 output(s) for total of 369.177714063000 dcy

stealth address amount amount idx
00: 2fb00df42a3009bb30a329126a5313bad23fd0925c555332cd6091c8b40b0479 369.177714063000 122769 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": 66640, "vin": [ { "gen": { "height": 66630 } } ], "vout": [ { "amount": 369177714063, "target": { "key": "2fb00df42a3009bb30a329126a5313bad23fd0925c555332cd6091c8b40b0479" } } ], "extra": [ 1, 202, 39, 65, 252, 35, 97, 213, 189, 43, 203, 212, 213, 88, 242, 141, 103, 178, 124, 86, 249, 210, 160, 206, 245, 125, 216, 236, 13, 97, 181, 33, 59, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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