Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02491203a55fa21382ca5eac3d77481d0ad97024f7fe2bc0d15f3902109d938c

Tx prefix hash: c5362c9c694cf13e9309702b94f7daa5f59ff8899063ca4703fd4a286cb12406
Tx public key: 85015f5134d3a837f8fd91c18d9d83cbeaa0af336f230f69b08da5e9135862d3
Timestamp: 1720808083 Timestamp [UCT]: 2024-07-12 18:14:43 Age [y:d:h:m:s]: 01:124:22:54:00
Block: 1064263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347818 RingCT/type: yes/0
Extra: 0185015f5134d3a837f8fd91c18d9d83cbeaa0af336f230f69b08da5e9135862d302110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 842c1533e8889469f8fba5cc9342921a23c5da5364939a2f6cdefda6e6cae272 0.600000000000 1534786 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": 1064273, "vin": [ { "gen": { "height": 1064263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "842c1533e8889469f8fba5cc9342921a23c5da5364939a2f6cdefda6e6cae272" } } ], "extra": [ 1, 133, 1, 95, 81, 52, 211, 168, 55, 248, 253, 145, 193, 141, 157, 131, 203, 234, 160, 175, 51, 111, 35, 15, 105, 176, 141, 165, 233, 19, 88, 98, 211, 2, 17, 0, 0, 0, 8, 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