Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06f165d22d9c0142e60482065c6e1c43705ca8267ce8a6fe12f8eb1b56f5f8e9

Tx prefix hash: 757e2e2b3a995e552ddfb7da88ba2cbc4c4f0bdf97712ec52c84ab878a860f43
Tx public key: e38d2cde5708381698b526ce71ce8e166b585949ca6712f5c6da85c851beddf1
Timestamp: 1716002056 Timestamp [UCT]: 2024-05-18 03:14:16 Age [y:d:h:m:s]: 00:322:11:23:57
Block: 1024401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230502 RingCT/type: yes/0
Extra: 01e38d2cde5708381698b526ce71ce8e166b585949ca6712f5c6da85c851beddf102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4aa322cd2df795eed5ac519e3c48a17bab6cdd0a6f61fdf0b432ed94a50d91f7 0.600000000000 1490132 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": 1024411, "vin": [ { "gen": { "height": 1024401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4aa322cd2df795eed5ac519e3c48a17bab6cdd0a6f61fdf0b432ed94a50d91f7" } } ], "extra": [ 1, 227, 141, 44, 222, 87, 8, 56, 22, 152, 181, 38, 206, 113, 206, 142, 22, 107, 88, 89, 73, 202, 103, 18, 245, 198, 218, 133, 200, 81, 190, 221, 241, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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