Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 058566860d5950ae7920013e795edcf1146f1debd695c81b84addf49899fdb65

Tx prefix hash: 311cca2f3c0b6c8dbc4fa9e0d053a3f62c6a2c47886e6edc965993d8d216945e
Tx public key: d0caaa2375a1283ab68781cd2df0e3f0ca041ae8b16a78f5ca338e92a1106229
Timestamp: 1759276490 Timestamp [UCT]: 2025-09-30 23:54:50 Age [y:d:h:m:s]: 00:007:23:17:10
Block: 1380050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5709 RingCT/type: yes/0
Extra: 01d0caaa2375a1283ab68781cd2df0e3f0ca041ae8b16a78f5ca338e92a110622902110000000ca5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a17cbc8f0b93bfedf43d8beaa1283e588949998291b458b62d34cb2b7e98477 0.600000000000 1868161 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": 1380060, "vin": [ { "gen": { "height": 1380050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a17cbc8f0b93bfedf43d8beaa1283e588949998291b458b62d34cb2b7e98477" } } ], "extra": [ 1, 208, 202, 170, 35, 117, 161, 40, 58, 182, 135, 129, 205, 45, 240, 227, 240, 202, 4, 26, 232, 177, 106, 120, 245, 202, 51, 142, 146, 161, 16, 98, 41, 2, 17, 0, 0, 0, 12, 165, 220, 205, 121, 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