Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 605d7bc929b9605b64e9fdf3dd4c09d465ac4be1d9e89257f5a344c898238deb

Tx prefix hash: d30a09f6d3111f7d9dc1f5178f9c4b23bacb4efe77e5964808aacfe3ec2e564f
Tx public key: f9e1ae075c03b0c377b288f161d3e5497730db64b2115830488a6d1e0d6b339b
Timestamp: 1577950373 Timestamp [UCT]: 2020-01-02 07:32:53 Age [y:d:h:m:s]: 04:262:09:09:25
Block: 37020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076613 RingCT/type: yes/0
Extra: 01f9e1ae075c03b0c377b288f161d3e5497730db64b2115830488a6d1e0d6b339b0211000000088a2ee0d9000000000000000000

1 output(s) for total of 462.741259443000 dcy

stealth address amount amount idx
00: 1ef687840ccdd62031c1fee4d4a9d4662a5ea4247db6989c900bfb7f762c7307 462.741259443000 62774 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": 37030, "vin": [ { "gen": { "height": 37020 } } ], "vout": [ { "amount": 462741259443, "target": { "key": "1ef687840ccdd62031c1fee4d4a9d4662a5ea4247db6989c900bfb7f762c7307" } } ], "extra": [ 1, 249, 225, 174, 7, 92, 3, 176, 195, 119, 178, 136, 241, 97, 211, 229, 73, 119, 48, 219, 100, 178, 17, 88, 48, 72, 138, 109, 30, 13, 107, 51, 155, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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