Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58da5ad20af59104ee255c5b1b5b863af040a97ce4e504dd89b58e4a082a0064

Tx prefix hash: ab04bfadd71a925107b0ef838332a82285491d4d685e023cf3665d43469185bc
Tx public key: 0f900249fe456fc9b8d40acc1df1f6063a74a512d8e3f1792b6409bf99c5489a
Timestamp: 1738512036 Timestamp [UCT]: 2025-02-02 16:00:36 Age [y:d:h:m:s]: 00:291:15:46:25
Block: 1210594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206206 RingCT/type: yes/0
Extra: 010f900249fe456fc9b8d40acc1df1f6063a74a512d8e3f1792b6409bf99c5489a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 829ebfc79be80e71d66ac00775e9c28b5b16f1edcab6ae7a4da44ae5cc9c3d1b 0.600000000000 1697347 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": 1210604, "vin": [ { "gen": { "height": 1210594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "829ebfc79be80e71d66ac00775e9c28b5b16f1edcab6ae7a4da44ae5cc9c3d1b" } } ], "extra": [ 1, 15, 144, 2, 73, 254, 69, 111, 201, 184, 212, 10, 204, 29, 241, 246, 6, 58, 116, 165, 18, 216, 227, 241, 121, 43, 100, 9, 191, 153, 197, 72, 154, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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