Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6edfc391e946f41cb6064230c817c45f836013aaa03ac459aca34ea411243d11

Tx prefix hash: b84dacfd4d970e7346e017552b18f32fcb45d87b30502dbdd8110eb1824cf342
Tx public key: d984b15c1b4d6a6558bfb5de49a7376cb460514ea7ab3c550a8a26ecce48b341
Timestamp: 1713425904 Timestamp [UCT]: 2024-04-18 07:38:24 Age [y:d:h:m:s]: 01:029:13:33:19
Block: 1003036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282098 RingCT/type: yes/0
Extra: 01d984b15c1b4d6a6558bfb5de49a7376cb460514ea7ab3c550a8a26ecce48b34102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c17c596e6257ef23f075a913733d4e4391ae1bcf0fb5d83090b9cbe99a5180f6 0.600000000000 1463566 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": 1003046, "vin": [ { "gen": { "height": 1003036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c17c596e6257ef23f075a913733d4e4391ae1bcf0fb5d83090b9cbe99a5180f6" } } ], "extra": [ 1, 217, 132, 177, 92, 27, 77, 106, 101, 88, 191, 181, 222, 73, 167, 55, 108, 180, 96, 81, 78, 167, 171, 60, 85, 10, 138, 38, 236, 206, 72, 179, 65, 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