Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57b8eeb0c956d8480d6c529e7bcd41e8ccb3cabd6850075f37bf68c2495cbf30

Tx prefix hash: 3a73ac117ea7e109c9eabc388342e3fb6e41a940eee6eb5a83e272345f2a1411
Tx public key: b0db336aa0a122ee566eb64692ccf512959bad07e5acbbcb68c142e111c1b78a
Timestamp: 1738882981 Timestamp [UCT]: 2025-02-06 23:03:01 Age [y:d:h:m:s]: 00:288:00:28:03
Block: 1213677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203603 RingCT/type: yes/0
Extra: 01b0db336aa0a122ee566eb64692ccf512959bad07e5acbbcb68c142e111c1b78a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5455c1e4a484977ddb31f7a87f32dbe7b418e2931ff8bf4f946db59fdf95c93f 0.600000000000 1700458 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": 1213687, "vin": [ { "gen": { "height": 1213677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5455c1e4a484977ddb31f7a87f32dbe7b418e2931ff8bf4f946db59fdf95c93f" } } ], "extra": [ 1, 176, 219, 51, 106, 160, 161, 34, 238, 86, 110, 182, 70, 146, 204, 245, 18, 149, 155, 173, 7, 229, 172, 187, 203, 104, 193, 66, 225, 17, 193, 183, 138, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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