Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5883df6dd30d38d488df43fad92f0ec68b1de659bc539894c76a2a07266cf290

Tx prefix hash: dc86591a6d2fcd6a17161ac96ab2db45b552d46cc45fd194b3c59f54d05f4f86
Tx public key: 4ff1ccd2120ff4e623bc8bb6b1f8e9e2d21f9c364990798de301ae05683ec898
Timestamp: 1742297569 Timestamp [UTC]: 2025-03-18 11:32:49 Age [y:d:h:m:s]: 01:248:03:22:31
Block: 1241959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441524 RingCT/type: yes/0
Extra: 014ff1ccd2120ff4e623bc8bb6b1f8e9e2d21f9c364990798de301ae05683ec898021100000006007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2fb182732f8af4a03d2a2129ec13f1dde27ac3bec635eed9062be76a114dddb3 0.000600000000 1728932 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": 1241969, "vin": [ { "gen": { "height": 1241959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fb182732f8af4a03d2a2129ec13f1dde27ac3bec635eed9062be76a114dddb3" } } ], "extra": [ 1, 79, 241, 204, 210, 18, 15, 244, 230, 35, 188, 139, 182, 177, 248, 233, 226, 210, 31, 156, 54, 73, 144, 121, 141, 227, 1, 174, 5, 104, 62, 200, 152, 2, 17, 0, 0, 0, 6, 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: