Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a2f95d969407c7da31e7bffd2cd7cd9b4bee50fcf3210b93cb93cf5a590bf9c

Tx prefix hash: 76ee7395bfcdec671048b969ae1212c9fe4e61ea51093d7eeb0a4d9983b1df26
Tx public key: fb3c2f6b20a15f08ef252c931b36f9fa4a363c1264dd4852cc0f3296758e4786
Timestamp: 1773006556 Timestamp [UTC]: 2026-03-08 21:49:16 Age [y:d:h:m:s]: 00:254:18:26:41
Block: 1493640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187596 RingCT/type: yes/0
Extra: 01fb3c2f6b20a15f08ef252c931b36f9fa4a363c1264dd4852cc0f3296758e4786021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd243594d8e5b03c036c609d74538e25e49b3f6532b0f66f5b45f137c38a7f89 0.000600000000 1983200 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": 1493650, "vin": [ { "gen": { "height": 1493640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd243594d8e5b03c036c609d74538e25e49b3f6532b0f66f5b45f137c38a7f89" } } ], "extra": [ 1, 251, 60, 47, 107, 32, 161, 95, 8, 239, 37, 44, 147, 27, 54, 249, 250, 74, 54, 60, 18, 100, 221, 72, 82, 204, 15, 50, 150, 117, 142, 71, 134, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: