Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd13f348fcda831840ceff1a15f5a06d0a46e01dc4b9e0167c80aa0fde6d34dc

Tx prefix hash: 2fe2efbdd84782621dc403fe9687c5a52aa590fc8dbdfd84e8b75628c1375084
Tx public key: 562d9daa4853783104cdb35575b99becf3c1cdb98d2359d7f98d37859b7a5e3d
Timestamp: 1771834319 Timestamp [UTC]: 2026-02-23 08:11:59 Age [y:d:h:m:s]: 00:265:09:40:36
Block: 1483939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195122 RingCT/type: yes/0
Extra: 01562d9daa4853783104cdb35575b99becf3c1cdb98d2359d7f98d37859b7a5e3d021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1ff8d8ebda09ff7df31389c738a3663df1ce4d9db8b96379a2f72fe4f49296e8 0.000600000000 1973351 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": 1483949, "vin": [ { "gen": { "height": 1483939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ff8d8ebda09ff7df31389c738a3663df1ce4d9db8b96379a2f72fe4f49296e8" } } ], "extra": [ 1, 86, 45, 157, 170, 72, 83, 120, 49, 4, 205, 179, 85, 117, 185, 155, 236, 243, 193, 205, 185, 141, 35, 89, 215, 249, 141, 55, 133, 155, 122, 94, 61, 2, 17, 0, 0, 0, 5, 228, 245, 25, 63, 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: