Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a034c984169bdc46724d2f2748757b46c8142cd6b72df65a653064642e3dbb3a

Tx prefix hash: e996304c61eb64ad80ebd455aa3047ee59b125e71e1b6fd54549b477efe23737
Tx public key: c8d813b7d3574e4dfa0c0454f34cb54810ee19082306303479b8f1eca445d366
Timestamp: 1758410203 Timestamp [UTC]: 2025-09-20 23:16:43 Age [y:d:h:m:s]: 01:060:23:26:30
Block: 1372879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310106 RingCT/type: yes/0
Extra: 01c8d813b7d3574e4dfa0c0454f34cb54810ee19082306303479b8f1eca445d366021100000006b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 272173668a02232910fb1cfc81a92e82181d010a91f232d19c6b0bfbf89636a3 0.000600000000 1860964 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": 1372889, "vin": [ { "gen": { "height": 1372879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "272173668a02232910fb1cfc81a92e82181d010a91f232d19c6b0bfbf89636a3" } } ], "extra": [ 1, 200, 216, 19, 183, 211, 87, 78, 77, 250, 12, 4, 84, 243, 76, 181, 72, 16, 238, 25, 8, 35, 6, 48, 52, 121, 184, 241, 236, 164, 69, 211, 102, 2, 17, 0, 0, 0, 6, 178, 247, 132, 196, 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: