Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ce422e5417a34b1c7fe4247ff3e0422cf013fd4cccfe3b365de062382f9b1b6

Tx prefix hash: 79acfdef75d091df24cd1c9071fd4ebd0ffc9ac017683f069a29f5b4caef3a85
Tx public key: 4fca1012da4123ef6e8beab5fd4064712dcedfd5f84d1bcf2afefdddfe573a67
Timestamp: 1745027947 Timestamp [UTC]: 2025-04-19 01:59:07 Age [y:d:h:m:s]: 01:029:03:41:34
Block: 1264534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271908 RingCT/type: yes/0
Extra: 014fca1012da4123ef6e8beab5fd4064712dcedfd5f84d1bcf2afefdddfe573a67021100000002dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 371ad1b5d389e84cfaec44d6f3e96b3400aaf0b992d344c7c3b7c03645aa35d5 0.000600000000 1751731 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": 1264544, "vin": [ { "gen": { "height": 1264534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "371ad1b5d389e84cfaec44d6f3e96b3400aaf0b992d344c7c3b7c03645aa35d5" } } ], "extra": [ 1, 79, 202, 16, 18, 218, 65, 35, 239, 110, 139, 234, 181, 253, 64, 100, 113, 45, 206, 223, 213, 248, 77, 27, 207, 42, 254, 253, 221, 254, 87, 58, 103, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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: