Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5df13f97c9b81f834e818065a2004e3fc5b96889442a93af6613bcfb6f64e22b

Tx prefix hash: 222734f41d57961e90463907d4dce6a167e2a13dcbae4fb5c83103458d31f284
Tx public key: f5fbb3a9b9e178f9a43e79caff1c55457e5433c1cf8a694034a3220e3f38c984
Timestamp: 1772637493 Timestamp [UTC]: 2026-03-04 15:18:13 Age [y:d:h:m:s]: 00:254:10:29:35
Block: 1490581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187220 RingCT/type: yes/0
Extra: 01f5fbb3a9b9e178f9a43e79caff1c55457e5433c1cf8a694034a3220e3f38c984021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bfb652297763586c9bffe3249092eae3ab3f3cc8c47e0a5a3bc616f8a70da72d 0.000600000000 1980087 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": 1490591, "vin": [ { "gen": { "height": 1490581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfb652297763586c9bffe3249092eae3ab3f3cc8c47e0a5a3bc616f8a70da72d" } } ], "extra": [ 1, 245, 251, 179, 169, 185, 225, 120, 249, 164, 62, 121, 202, 255, 28, 85, 69, 126, 84, 51, 193, 207, 138, 105, 64, 52, 163, 34, 14, 63, 56, 201, 132, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: