Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2175719b015e22a0c7e83049ba7b95e6a1aa5efc5749aa02cf5a9edb0ef4556

Tx prefix hash: 76753552a68cd9354b471f82b288329ad261d089d0ccb520a17e7811f850f975
Tx public key: 0efa647bd466610f4f4a3a5dfcb4522ea87a8b6c3dd2255899cb59748dd042b8
Timestamp: 1737461180 Timestamp [UTC]: 2025-01-21 12:06:20 Age [y:d:h:m:s]: 01:114:14:11:40
Block: 1202130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332667 RingCT/type: yes/0
Extra: 010efa647bd466610f4f4a3a5dfcb4522ea87a8b6c3dd2255899cb59748dd042b8021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a400975213af445977a5d295648ce8415004b3653b954f39b86f6a1511935eb1 0.000600000000 1688789 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": 1202140, "vin": [ { "gen": { "height": 1202130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a400975213af445977a5d295648ce8415004b3653b954f39b86f6a1511935eb1" } } ], "extra": [ 1, 14, 250, 100, 123, 212, 102, 97, 15, 79, 74, 58, 93, 252, 180, 82, 46, 168, 122, 139, 108, 61, 210, 37, 88, 153, 203, 89, 116, 141, 208, 66, 184, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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: