Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bb4ca380a4425a580358c37fb9e9acb73b34c053ad844ae721246e740878fc2

Tx prefix hash: b40ac1ced734eb66efac2cbf2652d8f3cafcfbd1c03ba59d85589d363efe1926
Tx public key: 474ad45caa0396f1ad4a82b77aa4d0a4376481780fbbba6f1255c0e39bec30a4
Timestamp: 1737480287 Timestamp [UCT]: 2025-01-21 17:24:47 Age [y:d:h:m:s]: 00:148:06:26:26
Block: 1202271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105705 RingCT/type: yes/0
Extra: 01474ad45caa0396f1ad4a82b77aa4d0a4376481780fbbba6f1255c0e39bec30a4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16c03b38746dcacd43e1c4e9f6c1ee729f9b475d6c0cb0f9bfb6d64b9ec772e0 0.600000000000 1688934 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": 1202281, "vin": [ { "gen": { "height": 1202271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16c03b38746dcacd43e1c4e9f6c1ee729f9b475d6c0cb0f9bfb6d64b9ec772e0" } } ], "extra": [ 1, 71, 74, 212, 92, 170, 3, 150, 241, 173, 74, 130, 183, 122, 164, 208, 164, 55, 100, 129, 120, 15, 187, 186, 111, 18, 85, 192, 227, 155, 236, 48, 164, 2, 17, 0, 0, 0, 2, 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