Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd8a12dbfd3f143eaa6f73ce81e24c894c55cfa1bada295e5950d55a351e1780

Tx prefix hash: 814fbf2c5c18d1c3210ddf14ba6d4204833cf629dbaebdef801f8ef20965c278
Tx public key: 86323f3c22fbc001bc4e6853b7b4120e752505087be959514dc4209fa9d8901e
Timestamp: 1695620277 Timestamp [UCT]: 2023-09-25 05:37:57 Age [y:d:h:m:s]: 02:040:22:24:27
Block: 855638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548896 RingCT/type: yes/0
Extra: 0186323f3c22fbc001bc4e6853b7b4120e752505087be959514dc4209fa9d8901e021100000007faf35c9c000000000000000000

1 output(s) for total of 0.897255568000 dcy

stealth address amount amount idx
00: 90dc6ca19eea5931b2ab37987a53254ab04ea961e5a9b48c7bc76e2f05fc3d42 0.897255568000 1309670 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": 855648, "vin": [ { "gen": { "height": 855638 } } ], "vout": [ { "amount": 897255568, "target": { "key": "90dc6ca19eea5931b2ab37987a53254ab04ea961e5a9b48c7bc76e2f05fc3d42" } } ], "extra": [ 1, 134, 50, 63, 60, 34, 251, 192, 1, 188, 78, 104, 83, 183, 180, 18, 14, 117, 37, 5, 8, 123, 233, 89, 81, 77, 196, 32, 159, 169, 216, 144, 30, 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