Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bb594277825da8cb1c596e9b1fa2dff98e525112850b3cb7859c1b019a5d107

Tx prefix hash: 023c999299fa66250e35da2bd4c755c68202e7ec5ee964c4831efd9962289308
Tx public key: 4d6a65fb2b1c6c83480a18d46d6dbeace82c314462be998fe546e506c2936dda
Timestamp: 1725593219 Timestamp [UCT]: 2024-09-06 03:26:59 Age [y:d:h:m:s]: 00:252:08:16:30
Block: 1103923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180221 RingCT/type: yes/0
Extra: 014d6a65fb2b1c6c83480a18d46d6dbeace82c314462be998fe546e506c2936dda021100000006e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: e450858416f810c65cc8529151e0be197e8f7c094ad4cc4c3a92c34ae80cb879 0.608000000000 1580938 of 0

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": 1103933, "vin": [ { "gen": { "height": 1103923 } } ], "vout": [ { "amount": 608000000, "target": { "key": "e450858416f810c65cc8529151e0be197e8f7c094ad4cc4c3a92c34ae80cb879" } } ], "extra": [ 1, 77, 106, 101, 251, 43, 28, 108, 131, 72, 10, 24, 212, 109, 109, 190, 172, 232, 44, 49, 68, 98, 190, 153, 143, 229, 70, 229, 6, 194, 147, 109, 218, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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