Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33a964820f60376c05e57bc32c97ebb60f9d78d2d85592f2d89ac7974b69e328

Tx prefix hash: db77f66e1ba60c16955effee767f07c7e026bdaf025b538aae42c31ff6fa5b88
Tx public key: 639b6b741f337db526b551421b7512b52c1c2042f5279c1cfdb92502b53c68d9
Timestamp: 1734598339 Timestamp [UCT]: 2024-12-19 08:52:19 Age [y:d:h:m:s]: 00:362:13:08:25
Block: 1178491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256644 RingCT/type: yes/0
Extra: 01639b6b741f337db526b551421b7512b52c1c2042f5279c1cfdb92502b53c68d90211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fe8be6f897b004105dc61e04c758688b9e12948707a73e1c50feab6a0c78ff2 0.600000000000 1664878 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": 1178501, "vin": [ { "gen": { "height": 1178491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fe8be6f897b004105dc61e04c758688b9e12948707a73e1c50feab6a0c78ff2" } } ], "extra": [ 1, 99, 155, 107, 116, 31, 51, 125, 181, 38, 181, 81, 66, 27, 117, 18, 181, 44, 28, 32, 66, 245, 39, 156, 28, 253, 185, 37, 2, 181, 60, 104, 217, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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