Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db81582b45035303e35ce37129cc16a4290348a7a122640fc83daadc3194d09a

Tx prefix hash: dfef977a64e2b9a8b8169e2f1aa8790690f691351797eea2eb4545171ec8ef51
Tx public key: 806b4a314294044a2399cfc8cef8ce66b55a6246a5891f59a195e8d816e38ae2
Timestamp: 1749749819 Timestamp [UCT]: 2025-06-12 17:36:59 Age [y:d:h:m:s]: 00:234:20:35:54
Block: 1303588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165518 RingCT/type: yes/0
Extra: 01806b4a314294044a2399cfc8cef8ce66b55a6246a5891f59a195e8d816e38ae2021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a10e9f40f1f6568869a251e3f00a6a1a7626e1823b6f9ea053da9253f94f17fc 0.600000000000 1791171 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": 1303598, "vin": [ { "gen": { "height": 1303588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a10e9f40f1f6568869a251e3f00a6a1a7626e1823b6f9ea053da9253f94f17fc" } } ], "extra": [ 1, 128, 107, 74, 49, 66, 148, 4, 74, 35, 153, 207, 200, 206, 248, 206, 102, 181, 90, 98, 70, 165, 137, 31, 89, 161, 149, 232, 216, 22, 227, 138, 226, 2, 17, 0, 0, 0, 1, 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