Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db4d75e690d026a769dc7ddb385259adeb62bbf89b6a3289288a5b043538eeae

Tx prefix hash: fcdc88fd780092777b0d0f601b7b1b553afce5861044eb6282ebf7d4c8ed6438
Tx public key: bad197e84d47a4db4faabf677ab617cb0378f0a9ab3ee266ee610434a7cf0d1b
Timestamp: 1772432632 Timestamp [UTC]: 2026-03-02 06:23:52 Age [y:d:h:m:s]: 00:258:18:26:31
Block: 1488880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190396 RingCT/type: yes/0
Extra: 01bad197e84d47a4db4faabf677ab617cb0378f0a9ab3ee266ee610434a7cf0d1b021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 695a2e855a8e366cf14def65ca8725c94c6d71f811b2c9a3dba97a9e57cbac3b 0.000600000000 1978362 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": 1488890, "vin": [ { "gen": { "height": 1488880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "695a2e855a8e366cf14def65ca8725c94c6d71f811b2c9a3dba97a9e57cbac3b" } } ], "extra": [ 1, 186, 209, 151, 232, 77, 71, 164, 219, 79, 170, 191, 103, 122, 182, 23, 203, 3, 120, 240, 169, 171, 62, 226, 102, 238, 97, 4, 52, 167, 207, 13, 27, 2, 17, 0, 0, 0, 3, 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: