Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54c92cf4c07e45c2ad2e14348e517345bced89d0e4ca243c8a533109b94b2690

Tx prefix hash: 2f4ead0fbc91e337af9e1caaed3ec2763bf94d69f71679b6d7b7521a54593b10
Tx public key: 075f0308e8d8b39ceecc2a8b6797b9af62671595698604715c0c493d00434fdf
Timestamp: 1711379644 Timestamp [UTC]: 2024-03-25 15:14:04 Age [y:d:h:m:s]: 01:351:15:21:15
Block: 986110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509927 RingCT/type: yes/0
Extra: 01075f0308e8d8b39ceecc2a8b6797b9af62671595698604715c0c493d00434fdf0211000000030011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 222e2ed4636820528bcb2e499a9512292409f26d11cc7b7a8399a5340eae2e7a 0.000600000000 1446335 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": 986120, "vin": [ { "gen": { "height": 986110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "222e2ed4636820528bcb2e499a9512292409f26d11cc7b7a8399a5340eae2e7a" } } ], "extra": [ 1, 7, 95, 3, 8, 232, 216, 179, 156, 238, 204, 42, 139, 103, 151, 185, 175, 98, 103, 21, 149, 105, 134, 4, 113, 92, 12, 73, 61, 0, 67, 79, 223, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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) | dinastycoin version: tesla-369