Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40c71f060b71fe4ced0f99ee4225fee412d7745f9609432d324bff214add7ef2

Tx prefix hash: 61f7428a70be45fe114c1d8ddb40cbfee0bce59f68a220aa5084ae3b144f38f5
Tx public key: d3b2ce8436f05c7ccea8741ab5fba7528bd7b674c77aeab9102cdf7bc7860bac
Timestamp: 1755228229 Timestamp [UCT]: 2025-08-15 03:23:49 Age [y:d:h:m:s]: 00:097:01:23:41
Block: 1346964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69046 RingCT/type: yes/0
Extra: 01d3b2ce8436f05c7ccea8741ab5fba7528bd7b674c77aeab9102cdf7bc7860bac021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19dd83b20564cb2884b490e55e56f49aae147a1eadce6e5bf8e6d843ca2e94a7 0.600000000000 1834875 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": 1346974, "vin": [ { "gen": { "height": 1346964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19dd83b20564cb2884b490e55e56f49aae147a1eadce6e5bf8e6d843ca2e94a7" } } ], "extra": [ 1, 211, 178, 206, 132, 54, 240, 92, 124, 206, 168, 116, 26, 181, 251, 167, 82, 139, 215, 182, 116, 199, 122, 234, 185, 16, 44, 223, 123, 199, 134, 11, 172, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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