Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2b80440af6ad0315b5c3c62f6b8a19d87af61ecc92b29c18b2fdfa1518851f6

Tx prefix hash: 8c14b30902d01a801c210a017a72a95655fbdd217b0b549849ce20e1cbbe5492
Tx public key: d152f275f06ea3bbade45038688192bd561b0455e840e3bc5f4171b4b5a3561d
Timestamp: 1761264408 Timestamp [UCT]: 2025-10-24 00:06:48 Age [y:d:h:m:s]: 00:075:14:52:05
Block: 1396552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54139 RingCT/type: yes/0
Extra: 01d152f275f06ea3bbade45038688192bd561b0455e840e3bc5f4171b4b5a3561d021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c4716fab25d35d0e4ac007e9bc1f21d550c69c9487aecc480fc7081c2c46c19 0.600000000000 1884839 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": 1396562, "vin": [ { "gen": { "height": 1396552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c4716fab25d35d0e4ac007e9bc1f21d550c69c9487aecc480fc7081c2c46c19" } } ], "extra": [ 1, 209, 82, 242, 117, 240, 110, 163, 187, 173, 228, 80, 56, 104, 129, 146, 189, 86, 27, 4, 85, 232, 64, 227, 188, 95, 65, 113, 180, 181, 163, 86, 29, 2, 17, 0, 0, 0, 2, 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