Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32a7ac581d06bdfdabd42d1496586038c76c4191f17de88e7b9861e2d7c659dc

Tx prefix hash: 00cacb14779f29279401ea9549532bb6e7287bf8d1cac8450601a79f48b01753
Tx public key: 557bdc0074a272a18b3699335d6811328a2b35a0c7d3719b4c000205a40fca9e
Timestamp: 1771316716 Timestamp [UTC]: 2026-02-17 08:25:16 Age [y:d:h:m:s]: 00:272:17:56:43
Block: 1479639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200438 RingCT/type: yes/0
Extra: 01557bdc0074a272a18b3699335d6811328a2b35a0c7d3719b4c000205a40fca9e021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 67376d703f5942af73d93fbb40b8bc417be30372f37505a4d2ee2f36356a9546 0.000600000000 1968993 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": 1479649, "vin": [ { "gen": { "height": 1479639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67376d703f5942af73d93fbb40b8bc417be30372f37505a4d2ee2f36356a9546" } } ], "extra": [ 1, 85, 123, 220, 0, 116, 162, 114, 161, 139, 54, 153, 51, 93, 104, 17, 50, 138, 43, 53, 160, 199, 211, 113, 155, 76, 0, 2, 5, 164, 15, 202, 158, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: