Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0a62126c301036d8b0ee9ce4e409e1c81a491dc2903ddb775492e5675d40a77

Tx prefix hash: 488d9c47203aa2d72527e16a67fb9ad27c48aaa898db5da9f3b5234c1007a83c
Tx public key: df2983ff946bed3e8ed5cf93f0a4f997e13ed202919047d3d8af283f442a7fdb
Timestamp: 1743299466 Timestamp [UTC]: 2025-03-30 01:51:06 Age [y:d:h:m:s]: 01:234:14:54:51
Block: 1250234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431788 RingCT/type: yes/0
Extra: 01df2983ff946bed3e8ed5cf93f0a4f997e13ed202919047d3d8af283f442a7fdb0211000000099ba629df000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2397d8155c9e393d8352415805407139649f3c7ce011ac1a2758830989ad3e1e 0.000600000000 1737281 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 dinastycoin-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": 1250244, "vin": [ { "gen": { "height": 1250234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2397d8155c9e393d8352415805407139649f3c7ce011ac1a2758830989ad3e1e" } } ], "extra": [ 1, 223, 41, 131, 255, 148, 107, 237, 62, 142, 213, 207, 147, 240, 164, 249, 151, 225, 62, 210, 2, 145, 144, 71, 211, 216, 175, 40, 63, 68, 42, 127, 219, 2, 17, 0, 0, 0, 9, 155, 166, 41, 223, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: