Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8a4f95f65f81cabcf57fdd03753ea1175ca8988981c0d1e59e8edf6b7c8dcf3

Tx prefix hash: d975cb3dd396873652c06260a42e8075c1c98dd0b3ce94bf5a5d04e1babc8f2d
Tx public key: 989ae379f2eb00288386e7becedd85b0c2749d23be6531e237df1b171335cfa9
Timestamp: 1736435598 Timestamp [UCT]: 2025-01-09 15:13:18 Age [y:d:h:m:s]: 00:159:21:49:51
Block: 1193676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113987 RingCT/type: yes/0
Extra: 01989ae379f2eb00288386e7becedd85b0c2749d23be6531e237df1b171335cfa90211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d050ed33fd2e07ff97b6450db2fe87144d748d2096bac7eae08e9aed68c8c125 0.600000000000 1680239 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": 1193686, "vin": [ { "gen": { "height": 1193676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d050ed33fd2e07ff97b6450db2fe87144d748d2096bac7eae08e9aed68c8c125" } } ], "extra": [ 1, 152, 154, 227, 121, 242, 235, 0, 40, 131, 134, 231, 190, 206, 221, 133, 176, 194, 116, 157, 35, 190, 101, 49, 226, 55, 223, 27, 23, 19, 53, 207, 169, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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