Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 294d3ca8c11e9b149edb1424e1c985dde0eabb4b77af21720298b403bf0294a1

Tx prefix hash: 7d62e66b053efd6df2c7a9fd3225ff829e0dd456770fec9e336097841e7b26af
Tx public key: 9a23dae41745728d95c4fbf4681449258d13db595a1e93a1e9aa4667239b6a1a
Timestamp: 1729877387 Timestamp [UCT]: 2024-10-25 17:29:47 Age [y:d:h:m:s]: 00:033:17:11:04
Block: 1139407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24089 RingCT/type: yes/0
Extra: 019a23dae41745728d95c4fbf4681449258d13db595a1e93a1e9aa4667239b6a1a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caba0f819524da21fa3ac2da1b3e271de5e4da83d24061f4eb1a6db1d280ba49 0.600000000000 1623194 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": 1139417, "vin": [ { "gen": { "height": 1139407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caba0f819524da21fa3ac2da1b3e271de5e4da83d24061f4eb1a6db1d280ba49" } } ], "extra": [ 1, 154, 35, 218, 228, 23, 69, 114, 141, 149, 196, 251, 244, 104, 20, 73, 37, 141, 19, 219, 89, 90, 30, 147, 161, 233, 170, 70, 103, 35, 155, 106, 26, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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