Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a634f4dbd58c8f21482147fdf81a57fa73a40ebc14a623d7c6c90207e8666385

Tx prefix hash: a53f58e33759970e14f7db270fde905a656864aa6e7a95710ff7085a6830b5d5
Tx public key: a0475cd95f33681f4d38ce40b3f37ef4b3d338219881d3043215439ff365da66
Timestamp: 1767459344 Timestamp [UTC]: 2026-01-03 16:55:44 Age [y:d:h:m:s]: 00:042:10:54:00
Block: 1447885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 30192 RingCT/type: yes/0
Extra: 01a0475cd95f33681f4d38ce40b3f37ef4b3d338219881d3043215439ff365da6602090000000cf3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: eaff53f214d7b5fd9e87c2094dfa8d17a3f974cbb41e7ca6b754dde168be1ec8 0.000600000000 1936847 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": 1447895, "vin": [ { "gen": { "height": 1447885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eaff53f214d7b5fd9e87c2094dfa8d17a3f974cbb41e7ca6b754dde168be1ec8" } } ], "extra": [ 1, 160, 71, 92, 217, 95, 51, 104, 31, 77, 56, 206, 64, 179, 243, 126, 244, 179, 211, 56, 33, 152, 129, 211, 4, 50, 21, 67, 159, 243, 101, 218, 102, 2, 9, 0, 0, 0, 12, 243, 179, 40, 84, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369