Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00a81d26cb46cf40d157bed5718a8fec9151a5a3bcba68594cddcdc2013e333e

Tx prefix hash: 1140f9771b02964ee858a8d72c6275d8e07b67c44789dbc76dedd83fe983ac9c
Tx public key: 60cd64407a7b2c1cfc7eb51538b54ea4a409ce2405610e5bb8afb473a3d58197
Timestamp: 1761845196 Timestamp [UCT]: 2025-10-30 17:26:36 Age [y:d:h:m:s]: 00:028:13:58:46
Block: 1401353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20462 RingCT/type: yes/0
Extra: 0160cd64407a7b2c1cfc7eb51538b54ea4a409ce2405610e5bb8afb473a3d58197021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 592dd73b47eeec8f6d129245ba7dd35c8a4b971cab4a7fcdc0bb1ca8e6e1f088 0.600000000000 1889672 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": 1401363, "vin": [ { "gen": { "height": 1401353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "592dd73b47eeec8f6d129245ba7dd35c8a4b971cab4a7fcdc0bb1ca8e6e1f088" } } ], "extra": [ 1, 96, 205, 100, 64, 122, 123, 44, 28, 252, 126, 181, 21, 56, 181, 78, 164, 164, 9, 206, 36, 5, 97, 14, 91, 184, 175, 180, 115, 163, 213, 129, 151, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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