Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f84ae894f7390c84a4d652abee28cb3fcce8ccd26f60850b20ffeda031fcb40f

Tx prefix hash: aa585690fbcb2a79763b522942e97303262e4caa074ef18afccc1b3bb4b6ded6
Tx public key: 0f6b71ad33af98fd8c4628b8e7e546694f4f21647ecf3076f73d7928a8243e2a
Timestamp: 1574746673 Timestamp [UCT]: 2019-11-26 05:37:53 Age [y:d:h:m:s]: 05:076:16:28:55
Block: 17678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197398 RingCT/type: yes/0
Extra: 010f6b71ad33af98fd8c4628b8e7e546694f4f21647ecf3076f73d7928a8243e2a021100000028354bbe3b000000000000000000

1 output(s) for total of 536.322883713000 dcy

stealth address amount amount idx
00: 8717cf9ce7cde171cc4fa97cbb4366d6fbaf70eda7b60e186f2ac5b96d1d8b3f 536.322883713000 26034 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": 17688, "vin": [ { "gen": { "height": 17678 } } ], "vout": [ { "amount": 536322883713, "target": { "key": "8717cf9ce7cde171cc4fa97cbb4366d6fbaf70eda7b60e186f2ac5b96d1d8b3f" } } ], "extra": [ 1, 15, 107, 113, 173, 51, 175, 152, 253, 140, 70, 40, 184, 231, 229, 70, 105, 79, 79, 33, 100, 126, 207, 48, 118, 247, 61, 121, 40, 168, 36, 62, 42, 2, 17, 0, 0, 0, 40, 53, 75, 190, 59, 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