Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ac7d586d0e8d109933eacef0f70f1e447ba88fb2a354378f706082cea672239

Tx prefix hash: 1206700ed840c7830e7bcfa19e3820a0d0ec50e80fc4f9e41963b6b8fb7bc813
Tx public key: 5a2a5d3947260ddf1dad834cca1f62e33ca5b71fbdec570de7453f1622d75041
Timestamp: 1767873070 Timestamp [UTC]: 2026-01-08 11:51:10 Age [y:d:h:m:s]: 00:039:19:08:37
Block: 1451315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28279 RingCT/type: yes/0
Extra: 015a2a5d3947260ddf1dad834cca1f62e33ca5b71fbdec570de7453f1622d75041021100000001215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8e435f2eedd6ec71734890d0d1d9f538b5e4f0a4e597601ba0fe6de5b7bc64bc 0.000600000000 1940325 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": 1451325, "vin": [ { "gen": { "height": 1451315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e435f2eedd6ec71734890d0d1d9f538b5e4f0a4e597601ba0fe6de5b7bc64bc" } } ], "extra": [ 1, 90, 42, 93, 57, 71, 38, 13, 223, 29, 173, 131, 76, 202, 31, 98, 227, 60, 165, 183, 31, 189, 236, 87, 13, 231, 69, 63, 22, 34, 215, 80, 65, 2, 17, 0, 0, 0, 1, 33, 91, 191, 137, 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) | dinastycoin version: tesla-369