Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f32c1d62e189ea45d2b79cd29e8ee848b253e0e4634153382b21076a7d36f98

Tx prefix hash: 8dae6b42cb5849fb062552191dc385e0173061cf957fd84ef95a351ec6ccfe6b
Tx public key: 2075267cdc3c81bdb89ecabbf9a950bf0710e56cd30dc0d5bba8813d6d4841dc
Timestamp: 1750158565 Timestamp [UCT]: 2025-06-17 11:09:25 Age [y:d:h:m:s]: 00:156:06:36:01
Block: 1306916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109474 RingCT/type: yes/0
Extra: 012075267cdc3c81bdb89ecabbf9a950bf0710e56cd30dc0d5bba8813d6d4841dc0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6593502cf88c50d4e8d5b9a20e09b052bcbae81e988dba33d4f790f35e5237d4 0.600000000000 1794525 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": 1306926, "vin": [ { "gen": { "height": 1306916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6593502cf88c50d4e8d5b9a20e09b052bcbae81e988dba33d4f790f35e5237d4" } } ], "extra": [ 1, 32, 117, 38, 124, 220, 60, 129, 189, 184, 158, 202, 187, 249, 169, 80, 191, 7, 16, 229, 108, 211, 13, 192, 213, 187, 168, 129, 61, 109, 72, 65, 220, 2, 17, 0, 0, 0, 1, 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