Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cf2fcf91b376a95a7ed03922c6dd4a5137698e13134ae0c76afedb83c86bcbe

Tx prefix hash: 31dacaca49aa9d963e679b650124ede12e8fe0faa81984cd4b9a78e08c24f3d9
Tx public key: 409bb32ad9f7482d4db45df851d56eb5aeef9aac833fe6d595023c006dd52bba
Timestamp: 1743465593 Timestamp [UTC]: 2025-03-31 23:59:53 Age [y:d:h:m:s]: 01:234:19:57:05
Block: 1251609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431885 RingCT/type: yes/0
Extra: 01409bb32ad9f7482d4db45df851d56eb5aeef9aac833fe6d595023c006dd52bba021100000006a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1316c0e2a2eccb3e1f4e150e81dca42e3f744b8f1a96a86bac2f1b5b83b8ee5a 0.000600000000 1738678 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": 1251619, "vin": [ { "gen": { "height": 1251609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1316c0e2a2eccb3e1f4e150e81dca42e3f744b8f1a96a86bac2f1b5b83b8ee5a" } } ], "extra": [ 1, 64, 155, 179, 42, 217, 247, 72, 45, 77, 180, 93, 248, 81, 213, 110, 181, 174, 239, 154, 172, 131, 63, 230, 213, 149, 2, 60, 0, 109, 213, 43, 186, 2, 17, 0, 0, 0, 6, 162, 237, 1, 107, 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: