Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fce02d6b55cac49182ed3dcbe81298dcc5c390276ab935325d0d34bf5ed7442

Tx prefix hash: 37cbe3e780f1db59abe7ea97b012527be434866091a4c5b6ff8c3d588d05e0ed
Tx public key: f8ab2ae0f82c31cfba84508110c767687604c20aa7c7e66e35138e8c81542229
Timestamp: 1576643307 Timestamp [UCT]: 2019-12-18 04:28:27 Age [y:d:h:m:s]: 04:338:00:40:23
Block: 28143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128747 RingCT/type: yes/0
Extra: 01f8ab2ae0f82c31cfba84508110c767687604c20aa7c7e66e35138e8c8154222902110000000e9159db1e000000000000000000

1 output(s) for total of 495.166691603000 dcy

stealth address amount amount idx
00: 4b211200d15523b17a2681f1e7a92528f2ac418bfdd2401e9f0453d8567af34f 495.166691603000 46673 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": 28153, "vin": [ { "gen": { "height": 28143 } } ], "vout": [ { "amount": 495166691603, "target": { "key": "4b211200d15523b17a2681f1e7a92528f2ac418bfdd2401e9f0453d8567af34f" } } ], "extra": [ 1, 248, 171, 42, 224, 248, 44, 49, 207, 186, 132, 80, 129, 16, 199, 103, 104, 118, 4, 194, 10, 167, 199, 230, 110, 53, 19, 142, 140, 129, 84, 34, 41, 2, 17, 0, 0, 0, 14, 145, 89, 219, 30, 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