Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29cdb37f93c90486497fd02ade5539499efd604b451d2d54d447a129b95d075a

Tx prefix hash: 0ccb24771bb0af6bdfcf14200090aec216529325dc6a40b86afc9107f15b59c1
Tx public key: c7f04a9ee949a242d0daa4cdb2098ce3a57dd171a25ba8a867adca1e37e574be
Timestamp: 1767466131 Timestamp [UTC]: 2026-01-03 18:48:51 Age [y:d:h:m:s]: 00:043:12:39:55
Block: 1447940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 30960 RingCT/type: yes/0
Extra: 01c7f04a9ee949a242d0daa4cdb2098ce3a57dd171a25ba8a867adca1e37e574be020900000001f3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8e5505874dac7b76335d3bda7443e7f5a34df914e6bdcc45c26ba033ccf71336 0.000600000000 1936902 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": 1447950, "vin": [ { "gen": { "height": 1447940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e5505874dac7b76335d3bda7443e7f5a34df914e6bdcc45c26ba033ccf71336" } } ], "extra": [ 1, 199, 240, 74, 158, 233, 73, 162, 66, 208, 218, 164, 205, 178, 9, 140, 227, 165, 125, 209, 113, 162, 91, 168, 168, 103, 173, 202, 30, 55, 229, 116, 190, 2, 9, 0, 0, 0, 1, 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