Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dc3ab91e11f7ff693367a663f0f05ea3f3f5b133a91ccd8b441da8628f778f5

Tx prefix hash: 4ceb756efd1e5c5fef748714b8f09b83aa2fea2e0991e1230d3128ca0331b44b
Tx public key: 2f00866d0edb06bdc8a64e714b51cfc76a2d92e530239f14079dfc431335d1e9
Timestamp: 1774921749 Timestamp [UTC]: 2026-03-31 01:49:09 Age [y:d:h:m:s]: 00:233:04:55:27
Block: 1509464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172239 RingCT/type: yes/0
Extra: 012f00866d0edb06bdc8a64e714b51cfc76a2d92e530239f14079dfc431335d1e9021100000003ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 640b31ec34a1a4fbea4561f420b836578c2d5a1fbbd2df8a848d01efdad6e586 0.000600000000 1999238 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": 1509474, "vin": [ { "gen": { "height": 1509464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "640b31ec34a1a4fbea4561f420b836578c2d5a1fbbd2df8a848d01efdad6e586" } } ], "extra": [ 1, 47, 0, 134, 109, 14, 219, 6, 189, 200, 166, 78, 113, 75, 81, 207, 199, 106, 45, 146, 229, 48, 35, 159, 20, 7, 157, 252, 67, 19, 53, 209, 233, 2, 17, 0, 0, 0, 3, 238, 75, 113, 129, 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: