Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00f43953e31248b439df05a1ae0e9b56f1a44976c59a75a6027ab1699b2f35b1

Tx prefix hash: e17fa4c90aa11a30e6fc90cffcb0bca0fcf43d31a74a6fd0341fe608170d8c56
Tx public key: 1764278e423a685e7e457e4b96c676ebcc21138e293d2ab66964188692be2312
Timestamp: 1578932080 Timestamp [UCT]: 2020-01-13 16:14:40 Age [y:d:h:m:s]: 05:097:10:10:53
Block: 44794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1219760 RingCT/type: yes/0
Extra: 011764278e423a685e7e457e4b96c676ebcc21138e293d2ab66964188692be23120211000000114943cd9f000000000000000000

1 output(s) for total of 436.093610656000 dcy

stealth address amount amount idx
00: d4a82f787475f430aa8af2b666016faf0eb305b650f5b86cf2894b0b15d23851 436.093610656000 81614 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": 44804, "vin": [ { "gen": { "height": 44794 } } ], "vout": [ { "amount": 436093610656, "target": { "key": "d4a82f787475f430aa8af2b666016faf0eb305b650f5b86cf2894b0b15d23851" } } ], "extra": [ 1, 23, 100, 39, 142, 66, 58, 104, 94, 126, 69, 126, 75, 150, 198, 118, 235, 204, 33, 19, 142, 41, 61, 42, 182, 105, 100, 24, 134, 146, 190, 35, 18, 2, 17, 0, 0, 0, 17, 73, 67, 205, 159, 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