Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89aeb402fc2ad401cdc1f7d11e34a4ec0d4e46dfeb2b0488cef7b617d9f7d75b

Tx prefix hash: c58dd74a2a7649697b1852c2a49cd97fa800e78b3a71652338d7b3e12f130c75
Tx public key: 69a37d3383a328a886f8b2cb400f05ca460b60a1255d645682bd86605036200e
Timestamp: 1738017509 Timestamp [UCT]: 2025-01-27 22:38:29 Age [y:d:h:m:s]: 00:045:17:20:31
Block: 1206529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32701 RingCT/type: yes/0
Extra: 0169a37d3383a328a886f8b2cb400f05ca460b60a1255d645682bd86605036200e0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efe3fb14555d0273976e9bdc3d7693fd5cb0e6eaa55ea1cd109a60c8f29d519d 0.600000000000 1693238 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": 1206539, "vin": [ { "gen": { "height": 1206529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efe3fb14555d0273976e9bdc3d7693fd5cb0e6eaa55ea1cd109a60c8f29d519d" } } ], "extra": [ 1, 105, 163, 125, 51, 131, 163, 40, 168, 134, 248, 178, 203, 64, 15, 5, 202, 70, 11, 96, 161, 37, 93, 100, 86, 130, 189, 134, 96, 80, 54, 32, 14, 2, 17, 0, 0, 0, 4, 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