Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5b17264666c2480d421a6bad71d1c35c45cd5e9c3d4342606d16488a10ee011

Tx prefix hash: 049760bd79172e6b94f63f2862075d045a1fd442700a4d7cfc46a85d36db095f
Tx public key: a41f7829f471fcc677fd01d3696a3a8dd625a0facf079315ec98e23cfdb3d5a3
Timestamp: 1709400780 Timestamp [UCT]: 2024-03-02 17:33:00 Age [y:d:h:m:s]: 00:253:12:52:47
Block: 969696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181506 RingCT/type: yes/0
Extra: 01a41f7829f471fcc677fd01d3696a3a8dd625a0facf079315ec98e23cfdb3d5a302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6f155033d7d66a13afc39d8a5b135b682f97cd7447b971f8744afff19ea25fe 0.600000000000 1429533 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": 969706, "vin": [ { "gen": { "height": 969696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6f155033d7d66a13afc39d8a5b135b682f97cd7447b971f8744afff19ea25fe" } } ], "extra": [ 1, 164, 31, 120, 41, 244, 113, 252, 198, 119, 253, 1, 211, 105, 106, 58, 141, 214, 37, 160, 250, 207, 7, 147, 21, 236, 152, 226, 60, 253, 179, 213, 163, 2, 17, 0, 0, 0, 3, 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