Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d0e773875eb99b21e40b0f7613c1a976c33145e2c5ca770301eb1a1e97d652e

Tx prefix hash: defac70139e69a768ad15f28e9bcc7f9e32e9a8e4f49820f5aeea5f8966b3ef1
Tx public key: 4d4720cf8c4f0c63fab7471a5ebdd4dd9c420065ef8fb98cb5596afdf922f815
Timestamp: 1728462016 Timestamp [UCT]: 2024-10-09 08:20:16 Age [y:d:h:m:s]: 00:170:13:01:55
Block: 1127699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121678 RingCT/type: yes/0
Extra: 014d4720cf8c4f0c63fab7471a5ebdd4dd9c420065ef8fb98cb5596afdf922f81502110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3eee2d0c7887872689de232c5e6edecdb654a23c37e53b39e671fbeca82f37d3 0.600000000000 1610510 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": 1127709, "vin": [ { "gen": { "height": 1127699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3eee2d0c7887872689de232c5e6edecdb654a23c37e53b39e671fbeca82f37d3" } } ], "extra": [ 1, 77, 71, 32, 207, 140, 79, 12, 99, 250, 183, 71, 26, 94, 189, 212, 221, 156, 66, 0, 101, 239, 143, 185, 140, 181, 89, 106, 253, 249, 34, 248, 21, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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