Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9986220dbd40c0aa4029da050b65affea6e96a0d7d60c0532641071571ea8869

Tx prefix hash: d9d18a0b7190e70f90a5b1517a8ec3a2da802642c7c6171b3dee8801d2b5f6bc
Tx public key: 0a25cb1af861196a7f40e48ccebef83b201a6809c16a08426e7fd08b7616c452
Timestamp: 1752327139 Timestamp [UCT]: 2025-07-12 13:32:19 Age [y:d:h:m:s]: 00:132:01:28:36
Block: 1323932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93088 RingCT/type: yes/0
Extra: 010a25cb1af861196a7f40e48ccebef83b201a6809c16a08426e7fd08b7616c4520211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2817effae16ca18f6c10689460786d56328b316b2fb758ffb44b415b346a120d 0.600000000000 1811673 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": 1323942, "vin": [ { "gen": { "height": 1323932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2817effae16ca18f6c10689460786d56328b316b2fb758ffb44b415b346a120d" } } ], "extra": [ 1, 10, 37, 203, 26, 248, 97, 25, 106, 127, 64, 228, 140, 206, 190, 248, 59, 32, 26, 104, 9, 193, 106, 8, 66, 110, 127, 208, 139, 118, 22, 196, 82, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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