Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1815106bfd0ca994a6cc9f36a82a769c9afe87941803a53b1da13cf742b0d4a

Tx prefix hash: 2e238854ef72555169c61d94ea6b7a4e15f43adee304540c508f874c1c6bfcc1
Tx public key: 01d14f0f66d3b7e8dfd73f4d7bbdd47097a1a9bb1e74e8871859712730e764c8
Timestamp: 1749957174 Timestamp [UCT]: 2025-06-15 03:12:54 Age [y:d:h:m:s]: 00:157:11:01:18
Block: 1305258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110313 RingCT/type: yes/0
Extra: 0101d14f0f66d3b7e8dfd73f4d7bbdd47097a1a9bb1e74e8871859712730e764c8021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62f0c026fce23d496ff84da66adc0ec674c1fe5a1e81aa1e23d7f5f71d352b95 0.600000000000 1792857 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": 1305268, "vin": [ { "gen": { "height": 1305258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62f0c026fce23d496ff84da66adc0ec674c1fe5a1e81aa1e23d7f5f71d352b95" } } ], "extra": [ 1, 1, 209, 79, 15, 102, 211, 183, 232, 223, 215, 63, 77, 123, 189, 212, 112, 151, 161, 169, 187, 30, 116, 232, 135, 24, 89, 113, 39, 48, 231, 100, 200, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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