Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 702c29fa37917e41bfef4c9bda36aa09f070f6cdf815533d6efcccf4f46861a8

Tx prefix hash: bd5d6b0887d794e215dc437b37e02fd87ff945c6a2058af29cbf937d6582eb83
Tx public key: 4c18afc8e03e601b6528ea0edc0ac8318bd85db822f23fdc8b1b5821a22de902
Timestamp: 1770285130 Timestamp [UTC]: 2026-02-05 09:52:10 Age [y:d:h:m:s]: 00:282:15:27:11
Block: 1471145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207386 RingCT/type: yes/0
Extra: 014c18afc8e03e601b6528ea0edc0ac8318bd85db822f23fdc8b1b5821a22de902021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b3f422b2329684dcfe4fa6ee1a9f27a853b452b141f99ae82d1b768dabf55c5c 0.000600000000 1960415 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": 1471155, "vin": [ { "gen": { "height": 1471145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3f422b2329684dcfe4fa6ee1a9f27a853b452b141f99ae82d1b768dabf55c5c" } } ], "extra": [ 1, 76, 24, 175, 200, 224, 62, 96, 27, 101, 40, 234, 14, 220, 10, 200, 49, 139, 216, 93, 184, 34, 242, 63, 220, 139, 27, 88, 33, 162, 45, 233, 2, 2, 17, 0, 0, 0, 1, 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: