Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5b4df7cdfdc623a43962c79b6f9aad24b81c8e4023c95b86eff76245baad17a

Tx prefix hash: c55abf2d3206ede7b5a3ccaf0fab8797d87e4cf0086cfa33f2be3f24865c5b63
Tx public key: 723b908b7d336cca1083552e2b26dcbb2dcf01b4e15d964449bd551a532e3ef8
Timestamp: 1739740284 Timestamp [UTC]: 2025-02-16 21:11:24 Age [y:d:h:m:s]: 01:091:22:14:48
Block: 1220743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317722 RingCT/type: yes/0
Extra: 01723b908b7d336cca1083552e2b26dcbb2dcf01b4e15d964449bd551a532e3ef8021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cfd9b91b684fcf7d5c276ceda861476f2ce44085a5b6951585a88b9ce4221a4d 0.000600000000 1707584 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": 1220753, "vin": [ { "gen": { "height": 1220743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfd9b91b684fcf7d5c276ceda861476f2ce44085a5b6951585a88b9ce4221a4d" } } ], "extra": [ 1, 114, 59, 144, 139, 125, 51, 108, 202, 16, 131, 85, 46, 43, 38, 220, 187, 45, 207, 1, 180, 225, 93, 150, 68, 73, 189, 85, 26, 83, 46, 62, 248, 2, 17, 0, 0, 0, 2, 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: