Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8ae50734333b22823bd9864ad55caab55abe653c1b59c99b2c4828d1c77d3c3

Tx prefix hash: 4c07e62ffad4d16fbfb9943ed004de990c2dcafd80e9482b4684da29108af730
Tx public key: b0519d79ad1aa0d8a4368d73e286f6aa36e0dbae57059c8b1a9afa8b0a6f1e15
Timestamp: 1697400899 Timestamp [UCT]: 2023-10-15 20:14:59 Age [y:d:h:m:s]: 01:175:12:19:47
Block: 870400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386453 RingCT/type: yes/0
Extra: 01b0519d79ad1aa0d8a4368d73e286f6aa36e0dbae57059c8b1a9afa8b0a6f1e15021100000007faf35c9c000000000000000000

1 output(s) for total of 0.801684536000 dcy

stealth address amount amount idx
00: c46835dbf7b61cb1c9ccd37ad54ee354fedd2c15735a335080baad1e6b6446d0 0.801684536000 1325279 of 0

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": 870410, "vin": [ { "gen": { "height": 870400 } } ], "vout": [ { "amount": 801684536, "target": { "key": "c46835dbf7b61cb1c9ccd37ad54ee354fedd2c15735a335080baad1e6b6446d0" } } ], "extra": [ 1, 176, 81, 157, 121, 173, 26, 160, 216, 164, 54, 141, 115, 226, 134, 246, 170, 54, 224, 219, 174, 87, 5, 156, 139, 26, 154, 250, 139, 10, 111, 30, 21, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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