Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a2ce9594cdef67f41f90ecf083f6eea78484ea573341f6f8489c95bea925c87

Tx prefix hash: 635e9d37b4a505651b0f214b447dda81d85bf1d88fd186e55e7ba0d84781a3de
Tx public key: a16166d29030ed932da8275af5a4d01d35da56ecea1e0910b7be44de0ac58211
Timestamp: 1707851019 Timestamp [UCT]: 2024-02-13 19:03:39 Age [y:d:h:m:s]: 01:060:13:27:39
Block: 956826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304336 RingCT/type: yes/0
Extra: 01a16166d29030ed932da8275af5a4d01d35da56ecea1e0910b7be44de0ac582110211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81e67d59de595c52f5b7d24141648b7f1a17922aa110b12dfef25a9b02f70f93 0.600000000000 1416136 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": 956836, "vin": [ { "gen": { "height": 956826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81e67d59de595c52f5b7d24141648b7f1a17922aa110b12dfef25a9b02f70f93" } } ], "extra": [ 1, 161, 97, 102, 210, 144, 48, 237, 147, 45, 168, 39, 90, 245, 164, 208, 29, 53, 218, 86, 236, 234, 30, 9, 16, 183, 190, 68, 222, 10, 197, 130, 17, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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