Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1384413f97a7083eb887f5a9f229192f695f1da4adb1b0411bea6709d1b9cda1

Tx prefix hash: 0c03033af0ef9cfb5164d920a4300341e2ed2085b6977bdaffab60e359182359
Tx public key: f1d57b0c01b846d4025b61922f66054309fe07fa6abe086bf7a515d1233fe781
Timestamp: 1766333355 Timestamp [UTC]: 2025-12-21 16:09:15 Age [y:d:h:m:s]: 00:057:09:35:41
Block: 1438543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40891 RingCT/type: yes/0
Extra: 01f1d57b0c01b846d4025b61922f66054309fe07fa6abe086bf7a515d1233fe7810211000000017b1e51ac000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5b54eac941ee182db1dac54fd0601e41b2a0b17fa8291e89f0054b540c48bd74 0.000600000000 1927364 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": 1438553, "vin": [ { "gen": { "height": 1438543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b54eac941ee182db1dac54fd0601e41b2a0b17fa8291e89f0054b540c48bd74" } } ], "extra": [ 1, 241, 213, 123, 12, 1, 184, 70, 212, 2, 91, 97, 146, 47, 102, 5, 67, 9, 254, 7, 250, 106, 190, 8, 107, 247, 165, 21, 209, 35, 63, 231, 129, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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