Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 444ff6bcfe02eb567812ebd4f61fcdeeab2e851cfb4928da707f8e621979dd51

Tx prefix hash: cf87c2bfd3710545d1065d6febb7358344f5551e31d8f198839db6d369a4a3ec
Tx public key: 461c0e9e02c4dc55227d5d5fb352769b32177321ee0ac4722f5891b0434c1c3e
Timestamp: 1767168498 Timestamp [UTC]: 2025-12-31 08:08:18 Age [y:d:h:m:s]: 00:070:11:25:34
Block: 1445466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 50240 RingCT/type: yes/0
Extra: 01461c0e9e02c4dc55227d5d5fb352769b32177321ee0ac4722f5891b0434c1c3e02090000000e0bb80a4400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a7c6d5e3127223f53f0870365e97da2171e26589282a27d2253055f239aa4378 0.000600000000 1934408 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": 1445476, "vin": [ { "gen": { "height": 1445466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7c6d5e3127223f53f0870365e97da2171e26589282a27d2253055f239aa4378" } } ], "extra": [ 1, 70, 28, 14, 158, 2, 196, 220, 85, 34, 125, 93, 95, 179, 82, 118, 155, 50, 23, 115, 33, 238, 10, 196, 114, 47, 88, 145, 176, 67, 76, 28, 62, 2, 9, 0, 0, 0, 14, 11, 184, 10, 68, 0 ], "rct_signatures": { "type": 0 } }


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