Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7f3aa4bbe61ed59a9a0a7f5a624220fd2294950ecdd52f515c9c2af82dd1ef3

Tx prefix hash: d727a8aa355cab313452fd1bc28db21a766c9e09409cd0273ac2be3fbc6f3db4
Tx public key: 360ba1711bd0a45dacd0b2f29dbb9d79e674c227646cfe236ff493deee0dd4c8
Timestamp: 1646031595 Timestamp [UCT]: 2022-02-28 06:59:55 Age [y:d:h:m:s]: 03:014:16:23:08
Block: 448170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 790561 RingCT/type: yes/0
Extra: 01360ba1711bd0a45dacd0b2f29dbb9d79e674c227646cfe236ff493deee0dd4c80211000000182e6b1fd5000000000000000000

1 output(s) for total of 20.092178474000 dcy

stealth address amount amount idx
00: eef2e0aab6f1a2a05b14a8e9ba3eed84a7143a459c36d6d6bfcdb1c8d8086609 20.092178474000 862471 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": 448180, "vin": [ { "gen": { "height": 448170 } } ], "vout": [ { "amount": 20092178474, "target": { "key": "eef2e0aab6f1a2a05b14a8e9ba3eed84a7143a459c36d6d6bfcdb1c8d8086609" } } ], "extra": [ 1, 54, 11, 161, 113, 27, 208, 164, 93, 172, 208, 178, 242, 157, 187, 157, 121, 230, 116, 194, 39, 100, 108, 254, 35, 111, 244, 147, 222, 238, 13, 212, 200, 2, 17, 0, 0, 0, 24, 46, 107, 31, 213, 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