Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4680521c5479b8cbed374cb2d914e7f63d2bc1da74fd1c65b357aa4f771821d8

Tx prefix hash: b5c39dfd18e67e6d0a02331da218f50c8c9b120884e5b8bfb1803e28a2f7f6f3
Tx public key: 829fe632673b80ab2752f6e3796945609521daee33ffae91e90993d29b9cbf98
Timestamp: 1728377201 Timestamp [UCT]: 2024-10-08 08:46:41 Age [y:d:h:m:s]: 00:106:12:12:30
Block: 1127009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76090 RingCT/type: yes/0
Extra: 01829fe632673b80ab2752f6e3796945609521daee33ffae91e90993d29b9cbf98021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55f8dff5b690114771a72580537f8b286f7a82e26cc18bd5bb4f67847b575e4c 0.600000000000 1609808 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": 1127019, "vin": [ { "gen": { "height": 1127009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55f8dff5b690114771a72580537f8b286f7a82e26cc18bd5bb4f67847b575e4c" } } ], "extra": [ 1, 130, 159, 230, 50, 103, 59, 128, 171, 39, 82, 246, 227, 121, 105, 69, 96, 149, 33, 218, 238, 51, 255, 174, 145, 233, 9, 147, 210, 155, 156, 191, 152, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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