Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b8d38f22a944ffcb4d72c5484fbb60b31c465243d7a122e5e1e708267f56a6f

Tx prefix hash: fe8418b2eec11a58360d50d65376385459cd294d068d440e0d40feb843050ab3
Tx public key: 1e47af22db947662d1473e72bb19dca65b5a2c9196cc2c7c8d2de718e1831317
Timestamp: 1744627704 Timestamp [UTC]: 2025-04-14 10:48:24 Age [y:d:h:m:s]: 01:031:07:09:20
Block: 1261225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273302 RingCT/type: yes/0
Extra: 011e47af22db947662d1473e72bb19dca65b5a2c9196cc2c7c8d2de718e1831317021100000009dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 27d0dc119a133bd497f82e3427367fc3af1348c7a2c1b9c86e3bd4e8cbf8a7e7 0.000600000000 1748392 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": 1261235, "vin": [ { "gen": { "height": 1261225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27d0dc119a133bd497f82e3427367fc3af1348c7a2c1b9c86e3bd4e8cbf8a7e7" } } ], "extra": [ 1, 30, 71, 175, 34, 219, 148, 118, 98, 209, 71, 62, 114, 187, 25, 220, 166, 91, 90, 44, 145, 150, 204, 44, 124, 141, 45, 231, 24, 225, 131, 19, 23, 2, 17, 0, 0, 0, 9, 219, 181, 113, 193, 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: