Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 315c9fdd8a8dae9080835f7a2b8ac0bf2cb65a15122fbe27d371f9017fe5a5e2

Tx prefix hash: d2f4a7c875253c6d3fa59ecc1e933b4c8e6a67cd8abefb40163070d5d646582a
Tx public key: f580049f6584ea2a4c22ae73998c9faba82050a69517ffd6602e66efeabb6f6f
Timestamp: 1749721010 Timestamp [UCT]: 2025-06-12 09:36:50 Age [y:d:h:m:s]: 00:156:07:51:16
Block: 1303369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109432 RingCT/type: yes/0
Extra: 01f580049f6584ea2a4c22ae73998c9faba82050a69517ffd6602e66efeabb6f6f021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f010f1e855adc346612349278bd365ff2e411d990059db70ed47844f0beb5827 0.600000000000 1790948 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 dinasty-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": 1303379, "vin": [ { "gen": { "height": 1303369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f010f1e855adc346612349278bd365ff2e411d990059db70ed47844f0beb5827" } } ], "extra": [ 1, 245, 128, 4, 159, 101, 132, 234, 42, 76, 34, 174, 115, 153, 140, 159, 171, 168, 32, 80, 166, 149, 23, 255, 214, 96, 46, 102, 239, 234, 187, 111, 111, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8