Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88147b0b9e99e43838a1f68d64d78b055de4d732f64b6025193fcd1e60cc153d

Tx prefix hash: 57d8df358447bd9e2981132e626d68a3eb69997f4453796227b822cec44a9e64
Tx public key: 0ba7389fabe43b57513685b664e743c342c8dc49f8f9e017b3c74cbd0b13f6ef
Timestamp: 1745899040 Timestamp [UTC]: 2025-04-29 03:57:20 Age [y:d:h:m:s]: 01:013:13:10:17
Block: 1271763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260488 RingCT/type: yes/0
Extra: 010ba7389fabe43b57513685b664e743c342c8dc49f8f9e017b3c74cbd0b13f6ef0211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1ead40c8678b0e90cb3eec50160c24a50fc48f763083620ffb3ef2ae9fdbc355 0.000600000000 1759030 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": 1271773, "vin": [ { "gen": { "height": 1271763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ead40c8678b0e90cb3eec50160c24a50fc48f763083620ffb3ef2ae9fdbc355" } } ], "extra": [ 1, 11, 167, 56, 159, 171, 228, 59, 87, 81, 54, 133, 182, 100, 231, 67, 195, 66, 200, 220, 73, 248, 249, 224, 23, 179, 199, 76, 189, 11, 19, 246, 239, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: