Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2fb19d48a539badafbb8053e50dea6da8d0f0c9a4e4a14b46cd6cc78b0fc158

Tx prefix hash: c0897c862eb9d9acd7091758fab521001b3a8e1091c334d6e263e480a0807a9f
Tx public key: 05294eb1877688cd1f0752006749a4a0e54bde5f0814b35d2218c3cb80d92964
Timestamp: 1709260123 Timestamp [UCT]: 2024-03-01 02:28:43 Age [y:d:h:m:s]: 01:036:06:06:20
Block: 968530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286909 RingCT/type: yes/0
Extra: 0105294eb1877688cd1f0752006749a4a0e54bde5f0814b35d2218c3cb80d9296402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d148b3481477bb13692292eb39edae3285748a1f5daec6fd96412bbc081c2cdd 0.600000000000 1428345 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": 968540, "vin": [ { "gen": { "height": 968530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d148b3481477bb13692292eb39edae3285748a1f5daec6fd96412bbc081c2cdd" } } ], "extra": [ 1, 5, 41, 78, 177, 135, 118, 136, 205, 31, 7, 82, 0, 103, 73, 164, 160, 229, 75, 222, 95, 8, 20, 179, 93, 34, 24, 195, 203, 128, 217, 41, 100, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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